<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>rrdbuild</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>



<h1 id="NAME">NAME</h1>

<p>rrdbuild - Instructions for building RRDtool</p>

<h1 id="OVERVIEW">OVERVIEW</h1>

<p>If you downloaded the source of RRDtool you have to compile it. This document will give some information on how this is done.</p>

<p>RRDtool relies on services of third part libraries. Some of these libraries may already be installed on your system. You have to compile copies of the other ones before you can build RRDtool.</p>

<p>This document will tell you about all the necessary steps to get going.</p>

<p>These instructions assume you are using a <b>bash</b> shell. If you use csh/tcsh, then you can either type <i>bash</i> to switch to bash for the compilation or if you know what you are doing just replace the export bits with setenv.</p>

<p>We further assume that your copies of <b>tar</b> and <b>make</b> are actually <b>GNU tar</b> and <b>GNU make</b> respectively. It could be that they are installed as <b>gtar</b> and <b>gmake</b> on your system.</p>

<h1 id="OPTIMISTIC-BUILD">OPTIMISTIC BUILD</h1>

<p>Before you start to build RRDtool, you have to decide two things:</p>

<ol>

<li><p>In which directory you want to build the software.</p>

</li>
<li><p>Where you want to install the software.</p>

</li>
</ol>

<p>Once you have decided. Save the two locations into environment variables.</p>

<pre><code> BUILD_DIR=/tmp/rrdbuild
 INSTALL_DIR=/opt/rrdtool-1.9.0</code></pre>

<p>If your <i>/tmp</i> is mounted with the option noexec (RHEL seems to do that) you have to choose a different directory!</p>

<p>Now make sure the BUILD_DIR exists and go there:</p>

<pre><code> mkdir -p $BUILD_DIR
 cd $BUILD_DIR</code></pre>

<p>Lets first assume you already have all the necessary libraries pre-installed.</p>

<pre><code> wget https://github.com/oetiker/rrdtool-1.x/releases/download/v1.8.0/rrdtool-1.9.0.tar.gz
 gunzip -c rrdtool-1.9.0.tar.gz | tar xf -
 cd rrdtool-1.9.0
 ./configure --prefix=$INSTALL_DIR &amp;&amp; make &amp;&amp; make install</code></pre>

<p>Ok, this was very optimistic. This try will probably have ended with <b>configure</b> complaining about several missing libraries.</p>

<h1 id="INSTALLING-DEPENDENCIES">INSTALLING DEPENDENCIES</h1>

<p>If your OS lets you install additional packages from a software repository, you may get away with installing the missing packages. When the packages are installed, run configure again and try to compile again. Below you find some hints on getting your OS ready for compiling RRDtool.</p>

<p>Additions to this list are welcome. In general RRDtool should work with the latest versions of the libraries. The versions listed here are just what was current when I tested this.</p>

<h2 id="OpenSolaris-2008.05">OpenSolaris 2008.05</h2>

<p>Just add a compiler and the gnome development package:</p>

<pre><code> pkg install sunstudioexpress
 pkg install SUNWgnome-common-devel</code></pre>

<p>There is a problem with <i>cairo.pc</i> on OpenSolaris. It suggests that xrender is required for compilation with cairo. This is not true and also bad since OpenSolaris does not include an <i>xrender.pc</i> file. Use Perl to fix this:</p>

<pre><code> perl -i~ -p -e &#39;s/(Requires.*?)\s*xrender.*/$1/&#39; /usr/lib/pkgconfig/cairo.pc</code></pre>

<p>Make sure the RRDtool build system finds your new compiler</p>

<pre><code> export PATH=/opt/SunStudioExpress/bin</code></pre>

<h2 id="Debian-Ubuntu">Debian / Ubuntu</h2>

<p>Use apt-get to make sure you have all that is required. A number of packages will get added through dependencies.</p>

<pre><code> apt-get install autoconf autopoint build-essential dc
 apt-get install groff-base libtool libpango1.0-dev libxml2-dev
 apt-get install python3-dev python3-setuptools</code></pre>

<h2 id="Gentoo">Gentoo</h2>

<p>In Gentoo installing RRDtool is really simple you just need to <b>emerge rrdtool</b>. All dependencies will be handled automatically by the portage system. The only thing you should care about are USE flags, which allow you fine tune features RRDtool will be built with. Currently the following USE flags are available:</p>

<pre><code> doc    - install .html and .txt documentation
          into /usr/share/doc/rrdtool-1.x.xx/
 perl   - build and install perl language bindings
 python - build and install python language bindings
 ruby   - build and install ruby language bindings
 tcl    - build and install tcl language bindings
 rrdcgi - build and install rrdcgi</code></pre>

<p>After you&#39;ve decided which USE flags you need, set them either in <i>make.conf</i> or <i>/etc/portage/package.use</i> and finally run:</p>

<pre><code> # emerge -va rrdtool</code></pre>

<p>Take a look at Gentoo handbook for further details on how to manage USE flags: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2</p>

<h1 id="BUILDING-DEPENDENCIES">BUILDING DEPENDENCIES</h1>

<p>But again this may have been too optimistic still, and you actually have to compile your own copies of some of the required libraries. Things like libpng and zlib are pretty standard so you will probably have them on your system anyway. Freetype, Fontinst, Cairo, Pango may be installed, but it is possible that they are pretty old and thus don&#39;t live up to our expectations, so you may want to compile their latest versions.</p>

<h2 id="General-build-tips-for-AIX">General build tips for AIX</h2>

<p>If you are working with AIX, you may find the <b>--disable-shared</b> option will cause things to break for you. In that case you may have to install the shared libraries into the RRDtool PREFIX and work with <b>--disable-static</b> instead.</p>

<p>Another hint to get RRDtool working on AIX is to use the IBM XL C Compiler:</p>

<pre><code> export CC=/usr/vac/bin/cc
 export PERLCC=$CC</code></pre>

<p>(Better instructions for AIX welcome!)</p>

<h2 id="Build-Instructions">Build Instructions</h2>

<p>Some libraries want to know where other libraries are. For this to work, set the following environment variable</p>

<pre><code> export PKG_CONFIG_PATH=${INSTALL_DIR}/lib/pkgconfig
 export PATH=$INSTALL_DIR/bin:$PATH</code></pre>

<p>The above relies on the presence of the <i>pkgconfig</i> program. Below you find instructions on how to compile pkgconfig.</p>

<p>Since we are compiling libraries dynamically, they must know where to find each other. This is done by setting an appropriate LDFLAGS. Unfortunately, the syntax again differs from system to system:</p>

<dl>

<dt id="Solaris">Solaris</dt>
<dd>

<pre><code> export LDFLAGS=-R${INSTALL_DIR}/lib</code></pre>

<p>if you are using the Sun Studio/Forte compiler, you may also want to set</p>

<pre><code> CFLAGS=&quot;-xO3 -xcode=pic13&quot;   (SPARC)
 CFLAGS=&quot;-xO3 -Kpic&quot;          (x86)</code></pre>

</dd>
<dt id="Linux">Linux</dt>
<dd>

<pre><code> export LDFLAGS=&quot;-Wl,--rpath -Wl,${INSTALL_DIR}/lib&quot;</code></pre>

</dd>
<dt id="HPUX">HPUX</dt>
<dd>

<pre><code> export LDFLAGS=&quot;+b${INSTALL_DIR}/lib&quot;</code></pre>

</dd>
<dt id="AIX">AIX</dt>
<dd>

<pre><code> export LDFLAGS=&quot;-Wl,-blibpath:${INSTALL_DIR}/lib&quot;</code></pre>

</dd>
</dl>

<p>If you have GNU make installed and it is not called &#39;make&#39;, then do</p>

<pre><code> export MAKE=gmake
 export GNUMAKE=gmake</code></pre>

<p>otherwise just do</p>

<pre><code> export MAKE=make</code></pre>

<h3 id="Building-pkgconfig">Building pkgconfig</h3>

<p>As mentioned above, without pkgconfig the whole build process will be lots of pain and suffering, so make sure you have a copy on your system. If it is not available natively, here is how to compile it.</p>

<pre><code> wget http://pkgconfig.freedesktop.org/releases/pkg-config-0.23.tar.gz
 gunzip -c pkg-config-0.23.tar.gz | tar xf -
 cd pkg-config-0.23
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<p>After installing pkgconfig in a custom directory, setting up the corresponding environment variable will be helpful.</p>

<pre><code> export PKG_CONFIG=$INSTALL_DIR/bin/pkg-config</code></pre>

<h3 id="Building-zlib">Building zlib</h3>

<p>Chances are very high that you already have that on your system ...</p>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/zlib-1.2.3.tar.gz
 gunzip -c zlib-1.2.3.tar.gz | tar xf -
 cd zlib-1.2.3
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot; --shared
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-libpng">Building libpng</h3>

<p>Libpng itself requires zlib to build, so we need to help a bit. If you already have a copy of zlib on your system (which is very likely) you can drop the settings of LDFLAGS and CPPFLAGS. Note that the backslash (\) at the end of lines means that the command is split over multiple lines.</p>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/libpng-1.2.18.tar.gz
 gunzip -c libpng-1.2.18.tar.gz | tar xf -
 cd libpng-1.2.18
 env CFLAGS=&quot;-O3 -fPIC&quot; ./configure --prefix=$INSTALL_DIR
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-freetype">Building freetype</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/freetype-2.3.5.tar.gz
 gunzip -c freetype-2.3.5.tar.gz | tar xf -
 cd freetype-2.3.5
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<p>If you run into problems building freetype on Solaris, you may want to try to add the following at the start the configure line:</p>

<pre><code> env EGREP=egrep</code></pre>

<h3 id="Building-LibXML2">Building LibXML2</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/libxml2-2.6.32.tar.gz
 gunzip -c libxml2-2.6.32.tar.gz | tar xf -
 cd libxml2-2.6.32
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-fontconfig">Building fontconfig</h3>

<p>Note that fontconfig has a run time configuration file in INSTALL_DIR/etc you may want to adjust that so that fontconfig finds the fonts on your system. Run the fc-cache program to build the fontconfig cache after changing the config file.</p>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/fontconfig-2.4.2.tar.gz
 gunzip -c fontconfig-2.4.2.tar.gz   | tar xf -
 cd fontconfig-2.4.2
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot; --with-freetype-config=$INSTALL_DIR/bin/freetype-config
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-Pixman">Building Pixman</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/pixman-0.10.0.tar.gz
 gunzip -c pixman-0.10.0.tar.gz  | tar xf -
 cd pixman-0.10.0
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-Cairo">Building Cairo</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/cairo-1.6.4.tar.gz
 gunzip -c cairo-1.6.4.tar.gz   | tar xf -
 cd cairo-1.6.4
 ./configure --prefix=$INSTALL_DIR \
    --enable-xlib=no \
    --enable-xlib-render=no \
    --enable-win32=no \
    CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<p>When building on Solaris you may want to do</p>

<pre><code> ./configure --prefix=$INSTALL_DIR \
    --enable-xlib=no \
    --enable-xlib-render=no \
    --enable-win32=no \
    CFLAGS=&quot;-O3 -fPIC -D_POSIX_PTHREAD_SEMANTICS&quot;</code></pre>

<h3 id="Building-Glib">Building Glib</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/glib-2.15.4.tar.gz
 gunzip -c glib-2.15.4.tar.gz  | tar xf -
 cd glib-2.15.4
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot;
 $MAKE
 $MAKE install</code></pre>

<h3 id="Building-Pango">Building Pango</h3>

<pre><code> cd $BUILD_DIR
 wget https://oss.oetiker.ch/rrdtool/pub/libs/pango-1.21.1.tar.bz2
 bunzip2 -c pango-1.21.1.tar.bz2 | tar xf -
 cd pango-1.21.1
 ./configure --prefix=$INSTALL_DIR CFLAGS=&quot;-O3 -fPIC&quot; --without-x
 $MAKE
 $MAKE install</code></pre>

<h2 id="Building-rrdtool-second-try">Building rrdtool (second try)</h2>

<p>Now all the dependent libraries are built and you can try again. This time you tell configure where it should be looking for libraries and include files. This is done via environment variables. Depending on the shell you are running, the syntax for setting environment variables is different.</p>

<p>And finally try building again. We disable the python and tcl bindings because it seems that a fair number of people have ill configured python and tcl setups that would prevent RRDtool from building if they are included in their current state.</p>

<pre><code> cd $BUILD_DIR/rrdtool-1.9.0
 ./configure --prefix=$INSTALL_DIR --disable-tcl --disable-python
 $MAKE clean
 $MAKE
 $MAKE install</code></pre>

<p>SOLARIS HINT: if you want to build the Perl module for the native Perl (the one shipping with Solaris) you will need the Sun Forte compiler installed on your box or you have to hand-tune bindings/perl-shared/Makefile while building!</p>

<p>Now go to <i>$INSTALL_DIR</i><b>/share/rrdtool/examples/</b> and run them to see if your build has been successful.</p>

<h1 id="AUTHOR">AUTHOR</h1>

<p>Tobias Oetiker &lt;tobi@oetiker.ch&gt;</p>


</body>

</html>


